[V2 Shims] Introduce locking at guestmanager layer#2638
Open
rawahars wants to merge 1 commit intomicrosoft:mainfrom
Open
[V2 Shims] Introduce locking at guestmanager layer#2638rawahars wants to merge 1 commit intomicrosoft:mainfrom
rawahars wants to merge 1 commit intomicrosoft:mainfrom
Conversation
Signed-off-by: Harsh Rawat <harshrawat@microsoft.com>
5b6939c to
8d94687
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
guestmanagercomponent is responsible for interacting with the guest agent to perform actions within the guest. There is no locking applicable directly at theGCSConnectionlevel and therefore, we introduce locking at this layer to prevent race conditions under concurrency scenarios.We do not need mutex locks in
vmmanageras it works directly on the compute system handle which locks the requests and handles concurrency.